Task: Raise Request For Change
This is the first step to trigger the Change Management Process. Whenever there is a need to change a technology configuration item, the Change Requester must raise a "Request For Change" and furnish it with requisite information.
Relationships
RolesPrimary Performer: Additional Performers:
Outputs
    Process Usage
    Main Description
    A change may be raised by a User, business, group representative support team, vendors, etc., based on a specific requirement. A Request For Change (RFC) must be created to initiate the Change Management process. This can be either done through phone, e-mail, on paper or through a web-based interface. Sometimes a Request For Change can also be a result of Incident Management, Event Management or Problem Management process, that needs a change for its resolution. In such cases a cross reference to incident, event or problem must be made in the RFC, so that there is link between the incident or problem and its resolution.

    While creating the RFC, the Change Requester should provide the description of change and its scope. The RFC should also include the business justification for the change, along with financial impacts, if any. It must detail out the benefits of implementing the change, risks of not implementing it, information on configuration items affected and the initial priority and category of the change.